Scheduling timelines of virtual machines

ABSTRACT

A method for scheduling timelines of virtual machines (VMs) is presented. The method includes determining, by a host controller device, a time span based on configurable timelines recorded in a plurality of timers stored in memory of the host controller device, wherein the time span comprises a time interval when a plurality of virtual machines (VMs) are started and does not include a run time of the plurality of VMs. The method further includes starting, by the host controller device during the determined time span, the plurality of VMs on a plurality of host machines managed by the host controller device, wherein start times of each of the plurality of VMs are distributed across the determined time span.

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.12/490,868, filed on Jun. 24, 2009, the entirety of which isincorporated herein by reference.

TECHNICAL FIELD

Embodiments of the present invention relate to a computer system, andmore specifically, to virtual machine management.

BACKGROUND

A virtual machine is a software implementation of a machine (computer)that includes its own operating system (referred to as a guest operatingsystem) and executes application programs. A host computer allocates acertain amount of its resources to each of the virtual machines, andmultiplexes its underlying hardware platform among the virtual machines.Each virtual machine is then able to use the allocated resources toexecute its guest operating system and applications. The software layerproviding the virtualization is commonly referred to as a hypervisor andis also known as a virtual machine monitor (VMM), a kernel-basedhypervisor, or part of a host operating system. The hypervisor emulatesthe underlying hardware of the host computer, making the use of thevirtual machine transparent to the guest operating system and the userof the computer.

A host computer can run multiple virtual machines simultaneously.Multiple host computers can be clustered together to provide a largenumber of virtual machines to an enterprise. In an enterprise, virtualmachines may need to be shut down or suspended at the end of each workday to perform certain maintenance tasks (e.g., software upgrades,backup, etc.). At the beginning of the next work day when the workerscome in, all of the virtual machines will be started at approximatelythe same time. Starting a large number of virtual machines can create aload spike that degrades the system performance.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example, and not by wayof limitation, and can be more fully understood with reference to thefollowing detailed description when considered in connection with thefigures in which:

FIG. 1 is a block diagram illustrating one embodiment of a host clustercontrolled by a host controller.

FIG. 2 is a block diagram illustrating one embodiment of a pre-schedulerin the host controller of FIG. 1.

FIG. 3 is an embodiment of a calendar according to which thepre-scheduler schedules the virtual machines.

FIG. 4 is a flow diagram illustrating a method for pre-scheduling thevirtual machines, in accordance with one embodiment of the presentinvention.

FIG. 5 illustrates a diagrammatic representation of a machine in theexemplary form of a computer system, in accordance with one embodimentof the present invention.

DETAILED DESCRIPTION

Described herein is a method and system for pre-scheduling the timelinesof virtual machines that run on a host cluster. In one embodiment, ahost controller uses a plurality of timers to determine the start timesof the virtual machines. The host controller starts the virtual machineson the host cluster over a time span according to the configurabletimelines recorded in the timers. The start times of the virtualmachines can be spread over the time span to prevent a load spike at anyparticular time instance. The virtual machines are up and running on thehosts by a pre-determined time to provide virtual desktops to remoteclients. In one embodiment, the timers may be configured as a calendar.

In the following description, numerous details are set forth. It will beapparent, however, to one skilled in the art, that the present inventionmay be practiced without these specific details. In some instances,well-known structures and devices are shown in block diagram form,rather than in detail, in order to avoid obscuring the presentinvention.

Some portions of the detailed descriptions which follow are presented interms of algorithms and symbolic representations of operations on databits within a computer memory. These algorithmic descriptions andrepresentations are the means used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm is here, and generally,conceived to be a self-consistent sequence of steps leading to a desiredresult. The steps are those requiring physical manipulations of physicalquantities. Usually, though not necessarily, these quantities take theform of electrical or magnetic signals capable of being stored,transferred, combined, compared, and otherwise manipulated. It hasproven convenient at times, principally for reasons of common usage, torefer to these signals as bits, values, elements, symbols, characters,terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise, as apparent from the followingdiscussion, it is appreciated that throughout the description,discussions utilizing terms such as “starting”, “running”, “recording”,“distributing”, or the like, refer to the action and processes of acomputer system, or similar electronic computing device, thatmanipulates and transforms data represented as physical (electronic)quantities within the computer system's registers and memories intoother data similarly represented as physical quantities within thecomputer system memories or registers or other such information storage,transmission or display devices.

The present invention also relates to an apparatus for performing theoperations herein. This apparatus may be specially constructed for therequired purposes, or it may comprise a general purpose computerselectively activated or reconfigured by a computer program stored inthe computer. Such a computer program may be stored in a computerreadable storage medium, such as, but not limited to, any type of diskincluding floppy disks, optical disks, CD-ROMs, and magnetic-opticaldisks, read-only memories (ROMs), random access memories (RAMs), EPROMs,EEPROMs, magnetic or optical cards, or any type of media suitable forstoring electronic instructions, each coupled to a computer system bus.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus. Various general purposesystems may be used with programs in accordance with the teachingsherein, or it may prove convenient to construct more specializedapparatus to perform the required method steps. The required structurefor a variety of these systems will appear as set forth in thedescription below. In addition, the present invention is not describedwith reference to any particular programming language. It will beappreciated that a variety of programming languages may be used toimplement the teachings of the invention as described herein.

The present invention may be provided as a computer program product, orsoftware, that may include a machine-readable medium having storedthereon instructions, which may be used to program a computer system (orother electronic devices) to perform a process according to the presentinvention. A machine-readable medium includes any mechanism for storingor transmitting information in a form readable by a machine (e.g., acomputer). For example, a machine-readable (e.g., computer-readable)medium includes a machine (e.g., a computer) readable storage medium(e.g., read only memory (“ROM”), random access memory (“RAM”), magneticdisk storage media, optical storage media, flash memory devices, etc.),a machine (e.g., computer) readable transmission medium (electrical,optical, acoustical or other form of propagated signals (e.g., carrierwaves, infrared signals, digital signals, etc.)), etc.

FIG. 1 illustrates an exemplary network architecture 100 in whichembodiments of the present invention may operate. The networkarchitecture 100 includes a cluster of hosts 103 (also referred to as“cluster” or “host cluster”) coupled to one or more clients 101 over anetwork 102. The network 102 may be a private network (e.g., a localarea network (LAN), a wide area network (WAN), intranet, etc.) or apublic network (e.g., the Internet). The cluster 103 includes aplurality of host computers 109 (also referred to as “hosts”). Thecluster 103 is also coupled to data storage 105. The data storage 105includes one or more mass storage devices (e.g., disks), which form astorage pool shared by all of the hosts 109 in the cluster 103.

The clients 101 may include computing devices that have a wide range ofprocessing capabilities. The client 101 may run client applications suchas a Web browser and a graphic user interface (GUI). The client 101 mayalso run other client applications, which receive multimedia datastreams or other data from one or more host computers 109 and re-directthe received data to a local display or other user interface.

Each host 109 may run one or more virtual machines 131. Each virtualmachine 131 runs a guest operating system (OS) that may be differentfrom one virtual machine to another. The guest OS may include MicrosoftWindows, Linux, Solaris, Mac OS, etc. Each host 109 may include ahypervisor 132 that emulates the underlying hardware platform for thevirtual machines 131. The hypervisor 132 may also be known as a virtualmachine monitor (VMM) or a kernel-based hypervisor. In some embodiments,the hypervisor 132 is part of a host operating system.

Each virtual machine 131 can be accessed by one or more of the clients101 over the network 102. In one scenario, each virtual machine 131provides a virtual desktop for the client 101. From the user's point ofview, the virtual desktop functions as a physical desktop (e.g., apersonal computer) and is indistinguishable from a physical desktop.

The hosts 109 can be managed by a host controller 107. The hostcontroller 107 may be a computer coupled to the cluster 103 directly orvia a network. Alternatively, the host controller 107 may be part of oneof the hosts 109. The host controller 107 may add a virtual machine,delete a virtual machine, balance the load on the cluster 103, poweron/off the hosts 109, provide directory service to the virtual machines131, and perform other managerial functions.

According to one embodiment of the present invention, the hostcontroller 107 includes a pre-scheduler 120 to schedule the time periodsduring which the virtual machines 131 are active. The start time of eachvirtual machine 131 can be scheduled such that the virtual machines 131do not start at the same time. In an enterprise environment, eachvirtual machine 131 provides a virtual desktop for the client 101. Atthe end of a work day, the virtual machines 131 are either suspended orshut down. In the morning of the next work day, all of the virtualdesktop users arrive at approximately the same time (e.g., 8:00 AM), andstart their virtual desktops at approximately the same time. Startingall of the virtual machines 131 at approximately the same time cancreate a load spike on the hosts 109. As the active periods of time forthe virtual machines 131 are predictable, the pre-scheduler 120 canpre-schedule the start time of each virtual machine 131 such that thevirtual machines 131 are up and running before the users arrive withoutcreating a load spike. For example, the start times of the virtualmachines 131 can be staggered over a time span (e.g., a couple of hours)to spread out the load. The virtual machines 131 can be grouped intomultiple groups of a moderate size (e.g., 10 virtual machines pergroup), with each group starting at a pre-determined time.

Operations of the pre-scheduler 120 will be described in greater detailwith references to FIGS. 2-4.

FIG. 2 illustrates an embodiment of the pre-scheduler 120 in the hostcontroller 107. The pre-scheduler 120 includes a load monitor 210 tomonitor the load on each host 109 (e.g., CPU utilization and memoryusage). For each host 109 that is currently active, the load monitor 210monitors the CPU utilization (also referred to as “CPU usage”) of thehost 109, and the lengths of time during which the CPU utilization isabove a high CPU utilization border (e.g., 80%) or under a lowutilization border (e.g., 20%). The load monitor 210 can determinewhether there is a load spike on each of the hosts 109.

In one embodiment, the pre-scheduler 120 pre-schedules the timelines(e.g., start time, suspend/stop time, resume time, etc.) of the virtualmachines 131 according to a calendar 220 stored in a memory 270. In oneembodiment, the calendar 220 is implemented by a plurality of timers260, which are configurable by a user (e.g., a system administrator).The calendar 220 may have a 24 (hour)/7 (day) format to define, at eachtime instance of a day, which virtual machine is to start, suspend/stop,etc. The calendar 220 may schedule the timelines on a recurring basis;e.g., the timelines are repeated every week. Alternatively, the calendar220 may be used to schedule a different timeline every single day. Thevirtual machines 131 may be divided into several groups by a groupingmodule 230. For example, each virtual machine 131 in a group may beassigned to run on a different host to avoid overloading a single host.As a result, the start times of the virtual machines 131 are spread overa time span. The load created by starting the virtual machines 131 canbe evenly distributed over the time span and over the hosts 109 in thecluster 103.

The calendar 220 is configurable by a user (e.g., a systemadministrator) to adapt the operations of the virtual machines 131 tochanging work environment and schedules. Alternatively, the calendar 220can be automatically modified by a load balancer 240 that modifies theload distribution specified by the calendar 220. For example, if theload monitor 210 observes a load spike when a group of virtual machinesstart, the user or the load balancer 240 may remove one or more virtualmachines from the group and records a different start time for these oneor more virtual machines in the calendar 220.

FIG. 3 illustrates an embodiment of the calendar 220. In thisembodiment, the calendar 220 records, for each day of the week, thetimelines of six groups of virtual machines (G₁-G₆). In alternativeembodiments, the virtual machines may be pre-scheduled individuallyinstead of as groups. For example, on Mondays, the start times of thesix groups are staggered over a period of two hours. The calendar 220also records the suspend time for the six groups at the end of the workday on Mondays. Similarly, the calendar 220 records the resume times andsuspend times for Tuesdays, Wednesdays and Thursdays. On Fridays, thecalendar 220 records the resume times and the stop times of the sixgroups. No activities are specified for Saturday and Sunday. Assume thatthe calendar 220 is used for an organization in which all of the virtualdesktop users report to work on 8 AM every Monday to Friday. Theembodiment of the calendar 220 allows that all of the six groups ofvirtual machines are started and ready for the users by 8:00 AM on thesework days.

The embodiment of the calendar 220 schedules the timelines of thevirtual machines on a weekly recurring basis. However, it is understoodthat the calendar 220 may have a different timeline for every singleday, if necessary. The calendar 220 can also be modified by thepre-scheduler 120 when there is a change to the host 109, the users,work projects, or any factor relating to the work environment oraffecting the work schedule.

In one embodiment, the calendar 220 can include the information thatassociates a given virtual machine with a particular host. Thus, thevirtual machine will start on a pre-scheduled time on the particularhost. The calendar 220 can also include configurable data of the virtualmachines. For example, a virtual machine may be scheduled to run on 2cores of a host on Mondays and only 1 core on the rest of the days. Asanother example, a virtual machine may be scheduled to use 2 gigabytesof memory on a host on Mondays and only 1 gigabytes of memory on therest of the days.

FIG. 4 is a flow diagram illustrating one embodiment of a method 400 forpre-scheduling virtual machines. The method 400 may be performed byprocessing logic 526 of FIG. 5 that may comprise hardware (e.g.,circuitry, dedicated logic, programmable logic, microcode, etc.),software (e.g., instructions run on a processing device to performhardware simulation), or a combination thereof. In one embodiment, themethod 400 is performed by the pre-scheduler 120 as a background process(FIGS. 1 and 2).

Referring to FIG. 4, the pre-scheduler 120 waits for a trigger to starta virtual machine according to the timelines recorded in the timers 260that are configured as the calendar 220 (block 410). The trigger may beincurred by one or more of the timers 260 that expire on pre-set timeinstances or intervals. When the pre-scheduler 120 receives the trigger,the pre-scheduler 120 starts the virtual machine on a host according toconfigurable data recorded in the calendar 220 (block 420). Theconfigurable data may include an identifier of the host that runs thevirtual machine, the number of cores to be used by the virtual machine,the memory usage of the virtual machine, etc. The pre-scheduler 120 thenreceives a trigger to suspend the virtual machine (block 430). Thetrigger arrives according to the timelines recorded in the calendar 220.The pre-scheduler 120 suspends the virtual machine in response to thetrigger. Subsequently, the pre-scheduler 120 receives a trigger toresume the virtual machine (block 440). The trigger arrives according tothe timelines recorded in the calendar 220. The pre-scheduler 120 thenresumes the virtual machine in response to the trigger. When a triggeris received to stop the virtual machine according to the calendar 220,the pre-scheduler 120 stops the virtual machine in response to thetrigger (block 450). The method 400 continues in the background when anext trigger to start the virtual machine is received by thepre-scheduler 120.

It is understood that some of the operations described above in themethod 400 may be omitted. For example, a virtual machine may be startedand stopped on a daily basis without being suspended or resumed. Avirtual machine may also be stopped (without being suspended) on one dayand suspended (without being stopped) on the next day.

FIG. 5 illustrates a diagrammatic representation of a machine in theexemplary form of a computer system 500 within which a set ofinstructions, for causing the machine to perform any one or more of themethodologies discussed herein, may be executed. In alternativeembodiments, the machine may be connected (e.g., networked) to othermachines in a Local Area Network (LAN), an intranet, an extranet, or theInternet. The machine may operate in the capacity of a server or aclient machine in a client-server network environment, or as a peermachine in a peer-to-peer (or distributed) network environment. Themachine may be a personal computer (PC), a tablet PC, a set-top box(STB), a Personal Digital Assistant (PDA), a cellular telephone, a webappliance, a server, a network router, switch or bridge, or any machinecapable of executing a set of instructions (sequential or otherwise)that specify actions to be taken by that machine. Further, while only asingle machine is illustrated, the term “machine” shall also be taken toinclude any collection of machines (e.g., computers) that individuallyor jointly execute a set (or multiple sets) of instructions to performany one or more of the methodologies discussed herein.

The exemplary computer system 500 includes a processor 502, a mainmemory 504 (e.g., read-only memory (ROM), flash memory, dynamic randomaccess memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM(RDRAM), etc.), a static memory 506 (e.g., flash memory, static randomaccess memory (SRAM), etc.), and a secondary memory 518 (e.g., a datastorage device), which communicate with each other via a bus 530.

The processor 502 represents one or more general-purpose processingdevices such as a microprocessor, central processing unit, or the like.More particularly, the processor 502 may be a complex instruction setcomputing (CISC) microprocessor, reduced instruction set computing(RISC) microprocessor, very long instruction word (VLIW) microprocessor,processor implementing other instruction sets, or processorsimplementing a combination of instruction sets. The processor 502 mayalso be one or more special-purpose processing devices such as anapplication specific integrated circuit (ASIC), a field programmablegate array (FPGA), a digital signal processor (DSP), network processor,or the like. The processor 502 is configured to execute the processinglogic 526 for performing the operations and steps discussed herein.

The computer system 500 may further include a network interface device508. The computer system 500 also may include a video display unit 510(e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)), analphanumeric input device 512 (e.g., a keyboard), a cursor controldevice 514 (e.g., a mouse), and a signal generation device 516 (e.g., aspeaker).

The secondary memory 518 may include a machine-readable storage medium(or more specifically a computer-readable storage medium) 531 on whichis stored one or more sets of instructions (e.g., software 522)embodying any one or more of the methodologies or functions describedherein. The software 522 may also reside, completely or at leastpartially, within the main memory 504 and/or within the processingdevice 502 during execution thereof by the computer system 500; the mainmemory 504 and the processing device 502 also constitutingmachine-readable storage media. The software 522 may further betransmitted or received over a network 520 via the network interfacedevice 508.

The machine-readable storage medium 531 may include the pre-scheduler120 of FIG. 2. While the machine-readable storage medium 531 is shown inan exemplary embodiment to be a single medium, the term“machine-readable storage medium” should be taken to include a singlemedium or multiple media (e.g., a centralized or distributed database,and/or associated caches and servers) that store the one or more sets ofinstructions. The term “machine-readable storage medium” shall also betaken to include any medium that is capable of storing or encoding a setof instructions for execution by the machine that cause the machine toperform any one or more of the methodologies of the present invention.The term “machine-readable storage medium” shall accordingly be taken toinclude, but not be limited to, solid-state memories, and optical andmagnetic media.

It is to be understood that the above description is intended to beillustrative, and not restrictive. Many other embodiments will beapparent to those of skill in the art upon reading and understanding theabove description. Although the present invention has been describedwith reference to specific exemplary embodiments, it will be recognizedthat the invention is not limited to the embodiments described, but canbe practiced with modification and alteration within the spirit andscope of the appended claims. Accordingly, the specification anddrawings are to be regarded in an illustrative sense rather than arestrictive sense. The scope of the invention should, therefore, bedetermined with reference to the appended claims, along with the fullscope of equivalents to which such claims are entitled.

What is claimed is:
 1. A method comprising: determining, by a hostcontroller device, a time span in view of configurable timelinesrecorded in a plurality of timers stored in memory of the hostcontroller device, wherein the time span comprises: a first timeinterval when a plurality of virtual machines (VMs) are at least one ofsuspended or shut down; the time interval when the plurality of VMs arenot active; and the time interval prior to an active period of use ofthe plurality of VMs by users; starting, by the host controller deviceduring the determined time span, the plurality of VMs on a plurality ofhost machines managed by the host controller device, wherein start timesof each of the plurality of VMs are distributed across the determinedtime span, and wherein the plurality of VMs are evenly distributedacross the plurality of host machines; and suspending, by the hostcontroller device, the plurality of VMs at an end of the active periodof use according to the configurable timeline, wherein the plurality ofVMs includes more than two VMs.
 2. The method of claim 1, furthercomprising, when the plurality of VMs are divided into a plurality ofgroups: associating a timer with each group of the plurality of VMs; andrecording, in the timers associated with the groups, a different starttime for each group.
 3. The method of claim 1, further comprising:associating a timer with each VM of the plurality of VMs; and recording,in the timer associated with the each VM, a start time and a stop timefor the VM on a recurring basis.
 4. The method of claim 1, furthercomprising: recording configurable timelines in a plurality of timersstored in a memory of the host controller device; and configuring theplurality of timers as a calendar.
 5. The method of claim 1, furthercomprising: distributing a load created by starting the plurality of VMsover the time span and over the plurality of host machines.
 6. Themethod of claim 1, further comprising: observing a load spike whenstarting one or more VMs of the plurality of VMs; and re-scheduling theone or more VMs to start at a different time.
 7. The method of claim 1,wherein starting the plurality of VMs further comprises: running each VMof the plurality of VMs according to configurable data recorded in aplurality of timers stored in a memory of the host controller device,wherein the configurable data comprises an identifier of a host machinethat runs the VM, the number of cores used by the VM, and a memory usageof the VM.
 8. A non-transitory computer readable storage mediumincluding instructions that, when executed by a processing device, causethe processing device to perform operations comprising: determining, bythe processing device of a host controller device, a time span in viewof configurable timelines recorded in a plurality of timers stored inmemory of the host controller device, wherein the time span comprises: afirst time interval when a plurality of virtual machines (VMs) are atleast one of suspended or shut down; the time interval when theplurality of VMs are not active; and the time interval prior to anactive period of use of the plurality of VMs by users; starting, by theprocessing device during the determined time span, the plurality of VMson a plurality of host machines managed by the host controller device,wherein start times of each of the plurality of VMs are evenlydistributed across the determined time span, and wherein the pluralityof VMs are distributed across the plurality of host machines; andsuspending, by the processing device, the plurality of VMs at an end ofthe active period of use according to the configurable timeline, whereinthe plurality of VMs includes more than two VMs.
 9. The non-transitorycomputer readable storage medium of claim 8, wherein the instructions,when executed by the processing device, cause the processing device toperform further operations comprising, when the plurality of VMs aredivided into a plurality of groups: associating a timer with each groupof the plurality of VMs; and recording, in the timers associated withthe groups, a different start time for each group.
 10. Thenon-transitory computer readable storage medium of claim 8, wherein theinstructions, when executed by the processing device, cause theprocessing device to perform further operations comprising: associatinga timer with each VM of the plurality of VMs; and recording, in thetimer associated with the each VM, a start time and a stop time for theVM on a recurring basis.
 11. The non-transitory computer readablestorage medium of claim 8, wherein the instructions, when executed bythe processing device, cause the processing device to perform furtheroperations comprising: recording configurable timelines in a pluralityof timers stored in a memory of the host controller device; andconfiguring the plurality of timers as a calendar.
 12. Thenon-transitory computer readable storage medium of claim 8, wherein theinstructions, when executed by the processing device, cause theprocessing device to perform further operations comprising: distributinga load created by starting the plurality of VMs over the time span andover the plurality of host machines.
 13. The non-transitory computerreadable storage medium of claim 8, wherein the instructions, whenexecuted by the processing device, cause the processing device toperform further operations comprising: observing a load spike whenstarting one or more VMs of the plurality of VMs; and re-scheduling theone or more VMs to start at a different time.
 14. The non-transitorycomputer readable storage medium of claim 8, wherein starting theplurality of VMs further comprises: running each VM of the plurality ofVMs according to configurable data recorded in a plurality of timersstored in a memory of the host controller device, wherein theconfigurable data comprises an identifier of a host machine that runsthe VM, the number of cores used by the VM, and a memory usage of theVM.
 15. A system comprising: a memory to store a plurality of timers; aprocessing device communicably coupled to the memory; and a hostcontroller executable from the memory by the processing device andcommunicably coupled to a plurality of host machines to run a pluralityof virtual machines (VMs), the host controller to: determine, a timespan in view of configurable timelines recorded in a plurality of timersstored in the memory, wherein the time span comprises: a first timeinterval when a plurality of virtual machines (VMs) are at least one ofsuspended or shut down; the time interval when the plurality of VMs arenot active; and the time interval prior to an active period of use ofthe plurality of VMs by users: start, during the determined time span,the plurality of VMs on a plurality of host machines managed by the hostcontroller device, wherein start times of each of the plurality of VMsare evenly distributed across the determined time span, and wherein theplurality of VMs are distributed across the plurality of host machines;and suspend the plurality of VMs at an end of the active period of useaccording to the configurable timeline, wherein the plurality of VMsincludes more than two VMs.
 16. The system of claim 15, wherein when theplurality of VMs are divided into a plurality of groups, the hostcontroller further to: associate a timer with each group of theplurality of VMs; and record, in the timers associated with the groups,a different start time for each group.
 17. The system of claim 15,further comprising: a load monitor to observe a load spike when startingone or more VMs of the plurality of VMs; and a load balancer tore-schedule the one or more VMs to start at a different time.
 18. Thesystem of claim 15, wherein the host controller further to: associate atimer with each VM of the plurality of VMs; and record, in the timerassociated with the each VM, a start time and a stop time for the VM ona recurring basis.
 19. The system of claim 15, wherein the hostcontroller further to: record configurable timelines in a plurality oftimers stored in a memory of the host controller device; and configurethe plurality of timers as a calendar.
 20. The system of claim 15,wherein starting the plurality of VMs further comprises the hostcontroller to: run each VM of the plurality of VMs according toconfigurable data recorded in a plurality of timers stored in a memoryof the host controller device, wherein the configurable data comprisesan identifier of a host machine that runs the VM, the number of coresused by the VM, and a memory usage of the VM.
 21. Thecomputer-implemented method of claim 1, wherein the distribution of thestart times of each of the plurality of VMs is an even distributionacross the determined time span.
 22. The non-transitory computerreadable storage medium of claim 8, wherein the distribution of thestart times of each of the plurality of VMs is an even distributionacross the determined time span.
 23. The system of claim 15, wherein thedistribution of the start times of each of the plurality of VMs is aneven distribution across the determined time span.